Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[chore][exporter/elasticsearch] Add more detail to version_conflict_engine_exception known issue #37150

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

carsonip
Copy link
Contributor

@carsonip carsonip commented Jan 10, 2025

Description

Add more detail to version_conflict_engine_exception known issue in README

```

2. If the problem persists, the error may be caused by metrics with data points with only nanosecond differences, as metric grouping is done in nanoseconds as opposed to milliseconds in while Elasticsearch checks for duplicates in milliseconds.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should remove that and instead truncate the timestamp by default.

but this will cause duplicate data in the same millisecond to be dropped silently.

As the default timestamp precision in ES is milliseconds, this will be the case regardless. We could add a config option in the exporter to retain the full nanosecond precision, which then also requires users to use date_nanos.

1. When sending different metrics with the same dimension (mostly made up of resource attributes, scope attributes, attributes),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm hoping we can remove this soon, when we resolve elastic/elasticsearch#99123

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants